This chapter discusses the tasks you must complete before you install and configure a SpinServer. These tasks include obtaining necessary IP addresses and designing a naming convention for system entities.
You need the following IP addresses before you begin the configuration of the SpinServer system components. Each set of ports must be on a separate IP subnet. Obtain these IP addresses from your network administrator.
An IP address is needed for the management software port (mgmt0) for each SpinServer. For remote access of the management interface, the port can be configured on a separate management LAN.
An IP address is needed for both SpinServer network ports (serv0 and serv1) for each SpinServer.
For clustering, an IP address is needed for both cluster ports (clus0 and clus1). For security reasons, cluster ports must be attached to a secure network. The cluster port must be configured even if only a single SpinServer is being installed to assure that all system components work together properly.
For ease of management of the SpinServer system and the data stored on it, you need to consider the names you choose for SpinServer system entities, including the SpinServers, virtual network interfaces, storage pools, virtual servers, and virtual file systems.
To prevent confusion and potential loss or misplacement of data, the names you choose must be orderly and easily recognizable by all system administrators who maintain the SpinServer system. Any naming system can be chosen for the system, but the following rules must be observed:
You enter the SpinServer ID into the system at the time you initially install the software. The name of the SpinServer is propagated from that initial installation into the management framework. The IDs for the SpinServers must be unique within a cluster.
After the ID for a SpinServer has been set, you cannot modify the server name or host name. To do so invalidates the failover port designation for the SpinServer and can result in the loss of data.
Storage pools names can be up to 32 characters long.
Virtual server names and VFS names can be 1 to 32 characters long, consisting of letters, numbers, period, and underscore. They must start with a letter or number. The names are case sensitive; for example, vs0, vS0, and Vs0 are all acceptable, different names for a virtual server.
Virtual file system names must be unique within a cluster. You cannot use the same virtual file system name on multiple virtual servers.
Copyright © 2004 Network Appliance, Inc.; copyright © 2003, 2004 Spinnaker Networks, LLC. All rights reserved. Specifications subject to change without notice.